Skip to content

Conversation

@ikraamg
Copy link
Contributor

@ikraamg ikraamg commented Mar 24, 2025

  • Make the PropertyUI type available in the destination configuration by moving it over (not sure about how to best do this).
  • Hide sensitive fields in the destination configuration UI.

Comment on lines +37 to +43
editor?:
| "ArrayTextarea"
| "StringArrayEditor"
| "CodeEditor"
| "SnippedEditor"
| "MultiSelectWithCustomOptions"
| string;
Copy link
Contributor Author

@ikraamg ikraamg Mar 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have added these types for ease of reference. They look to be the only ones currently supported. I have not removed the acceptance of the string type since there is a runtime check for the editor type and I wanted to tread lightly with this change.

@ikraamg ikraamg changed the title Avail cred ui types and hide sensitive destination fields in UI Avail SchemaUI types and hide sensitive fields in the destination configuration Mar 24, 2025
@ikraamg ikraamg marked this pull request as ready for review March 24, 2025 19:16
@ikraamg ikraamg changed the title Avail SchemaUI types and hide sensitive fields in the destination configuration Avail PropertyUI types and hide sensitive fields in the destination configuration Mar 24, 2025
import webhookIcon from "./icons/webhook";
import { branding } from "../branding";
import * as meta from "@jitsu/core-functions/src/meta";
import { HubspotCredentials } from "@jitsu/core-functions/src/meta";
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was already available via meta.HubspotCredentials

@ikraamg ikraamg closed this Oct 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants